Skip to content
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.

Support non-/usr content if ostree configured with overlayfs #570

Merged
merged 1 commit into from
Dec 11, 2023

Conversation

cgwalters
Copy link
Member

This pairs with ostreedev/ostree#3114

Basically if ostree has an overlayfs (whether writable or a readonly composefs), we're safe to handle non-/usr content.

However, we still always drop content from the
"API filesystems" like /run, /dev etc. Because really, no one should be adding stuff there.

@cgwalters
Copy link
Member Author

This obviates ostreedev/ostree#2681 for a container-oriented flow.

@cgwalters
Copy link
Member Author

I think this one should be pretty safe to get in

This pairs with ostreedev/ostree#3114

Basically if ostree has an overlayfs (whether writable or a readonly
composefs), we're safe to handle non-`/usr` content.

However, we still *always* drop content from the
"API filesystems" like `/run`, `/dev` etc.  Because really,
no one should be adding stuff there.
Copy link
Member

@jmarrero jmarrero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jmarrero jmarrero merged commit 49b4021 into ostreedev:main Dec 11, 2023
8 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants